NTISthis.com

Evidence Guide: ICADBS502A - Design a database

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICADBS502A - Design a database

What evidence can you provide to prove your understanding of each of the following citeria?

Determine database requirements

  1. Meet with client and conduct a user-needs analysis to determine database functionality
  2. Analyse results of user-needs analysis to identify technical requirements
  3. Develop a conceptual model of the database
  4. Submit conceptual model to client for review
  5. Evaluate client feedback and make changes as required
Meet with client and conduct a user-needs analysis to determine database functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse results of user-needs analysis to identify technical requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a conceptual model of the database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit conceptual model to client for review

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate client feedback and make changes as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop logical data model

  1. Identify attributes and determine data types
  2. Undertake normalisation of attributes
  3. Develop entity relationship diagram to clarify cardinality of relationships
  4. Document attributes, normalised data and entity relationship diagram
  5. Forward documentation to client for confirmation
Identify attributes and determine data types

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Undertake normalisation of attributes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop entity relationship diagram to clarify cardinality of relationships

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document attributes, normalised data and entity relationship diagram

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Forward documentation to client for confirmation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design data structures

  1. Confirm primary and foreign keys for tables
  2. Review client business rules
  3. Identify referential integrity constraints
  4. Establish database-management system constraints and incorporate into database design
  5. Develop validation rules for data
  6. Design indexes and develop data dictionary
  7. Document the database design
Confirm primary and foreign keys for tables

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review client business rules

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify referential integrity constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish database-management system constraints and incorporate into database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop validation rules for data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design indexes and develop data dictionary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design queries, screens and reports

  1. Design user interface for database, including menus, input screens and outputs
  2. Design queries based on requirements
  3. Design output reports based on requirements
  4. Compare physical design with conceptual model or user-needs analysis
  5. Incorporate changes as required
Design user interface for database, including menus, input screens and outputs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design queries based on requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design output reports based on requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare physical design with conceptual model or user-needs analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Incorporate changes as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design access and security systems

  1. Review business security plan as basis for commencing access and security design
  2. Design password and access system for database
  3. Identify multiple-user requirements
  4. Develop client access profiles using client business model
Review business security plan as basis for commencing access and security design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design password and access system for database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify multiple-user requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop client access profiles using client business model

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm database design

  1. Identify database backup and recovery requirements
  2. Develop and document the database backup and restore procedures
  3. Submit database and documentation to client for final approval
Identify database backup and recovery requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop and document the database backup and restore procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit database and documentation to client for final approval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

design a well-structured database that represents the client's business reality and provides the user with a productive business tool.

Context of and specific resources for assessment

Assessment must ensure access to:

current industry-accepted database software, network or other system for remote or multi-user access

business requirements

CASE or diagramming software

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

observation of candidate liaising with client

verbal or written questioning to assess candidate’s knowledge of:

normalisation

indexing

security models

review of the final database and associated support documentation.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Required Skills and Knowledge

Required skills

analytical skills to determine data objects required, data structures and business requirements

communication skills to liaise with clients

literacy skills to:

produce database documentation

produce models

numeracy skills to calculate field lengths, table and database estimated size

planning and organisational skills to undertake business analysis

problem-solving skills to solve normalisation problems

technical skills to undertake data modelling and structured query language (SQL) programming.

Required knowledge

data analysis, particularly in determining data types and data structures and query and report design

data modelling related to developing the conceptual data model

data redundancy

database management system (DBMS) fundamentals, particularly during the design phase

encryption and authentication as they apply to database security features

function and features of data types and data structures

functions and features of databases

logical design concepts, particularly related to designing data structures, queries screens and reports

object model design concepts, particularly related to designing data structures, queries, screens and reports

scalability of databases.

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Client may include:

employees

external organisations

individuals

internal departments.

Database may include:

commercial off-the-shelf (COTS) database packages

object-relational databases

proprietary databases

relational databases.

Technical requirements may relate to:

business

database

network

people in the organisation

platform

system.

Documentation may include:

audit trails

data dictionaries

entity-relationship diagrams

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards

naming standards

project management templates and report writing principles

version control.

Database management system may include:

distributed or centralised

online

partitioned geographically or thematically distributed.

Requirements may relate to:

business

database

network

people in the organisation

platform

system.

Security plan may include:

authentication

authorisation and integrity

privacy

security objectives of the organisation.